Fix release tag availability check - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
git ls-remote --exit-codeWhy
The first
1.0.1release run stopped in its pre-publication guard. An absent tag intentionally caused Git to exit with code 2, but the GitHub PowerShell runner terminated the step before the workflow could inspect that code.No tag, GitHub Release, or NuGet package was created by the failed run.
Impact
The guard now recognizes an absent tag without producing a native-command failure while preserving the existing protection against duplicate tags.
Validation
v1.0.1git diff --check